feat(feedback): Add screenshot attachment button to user feedback widget - #5828

Use term "screenshot" everywhere
Improve nullability handling

…hot-attachment

… buttons

The form was not scrollable, so in landscape or at large font scales the
send and cancel buttons were pushed off screen and the dialog could not
be dismissed. Wraps it in a ScrollView.

Also replaces the three full width buttons with the framework dialog
button bar: cancel and send sit in a right aligned bar, and the
screenshot button becomes a borderless full width action.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

…hot-attachment

# Conflicts:
#	CHANGELOG.md
#	sentry-android-core/src/main/java/io/sentry/android/core/SentryUserFeedbackForm.java
#	sentry-android-core/src/test/java/io/sentry/android/core/SentryUserFeedbackFormTest.kt
#	sentry/api/sentry.api
#	sentry/src/main/java/io/sentry/SentryFeedbackOptions.java
#	sentry/src/main/java/io/sentry/SentryOptions.java
#	sentry/src/test/java/io/sentry/SentryFeedbackOptionsTest.kt

androidx.activity is a compileOnly dependency, so the version in the app's
apk is outside our control and may be missing the photo picker APIs this
was compiled against. Catches LinkageError locally at the two call sites
that link against it, then falls back to the sanctioned
ExceptionUtils.rethrowIfFatal pattern, as ExceptionUtils documents and
SentrySQLiteDriver.hasConnectionPool demonstrates.

Registration is now guarded too, so a version mismatch hides the
screenshot button instead of breaking the whole form.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* docs(agents): Remove duplicated build commands and rules

AGENTS.md is force-read at the start of every session, so anything stated
there costs context on every task. Several rules had accumulated multiple
copies of themselves within that one file.

`spotlessApply`/`apiDump` was stated five times in AGENTS.md; it is now
stated once as a command and once as a workflow step, with the underlying
facts (Spotless enforces formatting, `.api` files are generated) kept where
they belong. The Testing command block is dropped in favour of the `test`
skill, which already resolves the per-module task and the unit-vs-system
split and does not drift. The Repository Skills bullet list restated skill
descriptions that the harness already injects, so it is now a pointer.

In the rules, `new_module.mdc`'s "Important Notes" was a verbatim
restatement of the AGENTS.md contributing guidelines, and `api.mdc` repeated
the opt-in-by-default rule in passing; both now defer to their canonical
homes.

No guidance is lost — every removed line is still stated somewhere that is
loaded when it applies.

* docs(agents): Refresh new_module rule and cover full system-test runs

Validating the previous commit with agents surfaced two gaps.

`new_module.mdc` had drifted from the repo. Its README badge snippet still
used the retired maven-badges.herokuapp.com format, while every current row
in README.md uses shields.io with a central.sonatype.com link. It also never
mentioned four steps that every existing integration module performs: the
`SENTRY_*_SDK_NAME` constant in `Config.kt` consumed by buildConfig and the
jar manifest, the `libs.versions.toml` entry paired with a `compileOnly`
dependency, self-registration via `SentryIntegrationPackageStorage.addPackage`
and `addIntegrationToSdkVersion`, and the integrations dropdown in the issue
template. It now also points at `sentry-kafka` and `sentry-android-timber` as
build-script templates, and records that `sentry-bom` and the root build file
need no change because they iterate over subprojects.

The `test` skill only ever ran a single module, so folding the AGENTS.md
testing block into it dropped the only reference to running the whole system
test suite. Step 3b now covers `make systemTest` and `make systemTestInteractive`.